[DE]Momaw

I tried using a Penta, and facing away from the components when pressing the "detonate" button but was able to complete the pulse turbine without issue. What specifically did you mean by  "AOE with delayed damage"?

We'd definitely love to fix this issue because this isn't the first time people have mentioned problems, but personally I have never seen this break. Not once. If people are seeing it "all the time",  it's something very specific that doesn't affect all players.  Video of the entire mission leading up to the point where it breaks would be fantastic!  Screenshots of a door that won't open doesn't help us at all unfortunately.

13 hours ago, Tahoma said:

I won't leave you completely empty-handed - go look at the Steam hardware survey, then assume the numbers there could be potentially even lower within Warframe's own playerbase. After that, you could look at the release information for various versions of DirectX. I think you'll find it unlikely that any GPU released after 2010 does not support DIrectX11.

No doubt the developers did the math, and decided that its no longer worth supporting a graphics API that has been considered outdated for the past decade.

Sorry mate.

Just to provide some grounding in data, yes, our statistics indicate that last week fewer than 0.1% of players were using DirectX 10 on video cards that could only do DirectX 10.  We published a warning that DirectX 10 support was ending, ...

26 minutes ago, -Kushina-Namikaze- said:

My game crash all time on login screen. Any ideas why?

You have not submitted any crash reports. Do you not get the crash handler? If you do, it's vitally important that you type in a description of what you were doing (even if it's just "I was on the login screen")  and send it to us.

This should now be resolved as of update 29.6.8. If you continue to have ongoing problems with the skin after 29.6.8,  please make it clear that you have tested more recently so we can distinguish between active issues and old echoes.

54 minutes ago, Tavanaka said:

I would actually love to hear a programmer talk about this

The relevant weapon ninjas declined to be interviewed on camera, but they did say this in response:

When we originally shipped [the Flak Cannon skin] we would replace the entire projectile with one based on the Drakgoon's projectiles (normal, charged, Conclave), with the new visuals and sounds. However, this essentially nerfed the Kuva Drakgoon since it would fire projectiles that were based on the base Drakgoon, not the Kuva variant.

In Hotfix 29.6.6, we changed it to override the visuals and sounds rather than replace the projectile completely. This maintains the expected damage, but makes it trickier to decide what to keep and what to replace as far as visuals/sounds, which there can be quite a selection of for things like bounce, embed, timed detonation, impact detonation, and radial dam...

We're aware of this issue and a fix is coming soon.

Speaking to the "Why is this so hard?" discussion, the simple fact is that we haven't reskinned a weapon's projectiles before except for bows which are their own specific animal. So there's some new infrastructure that has to be built behind the scenes to allow this. The bug where Stahlta fails to explode on alt fire is a direct result of fixing the issue where the Unreal skins would cause a Kuva weapon to behave as if it was the non-Kuva base variant. I know it's frustrating, but please bear with us while we bang this into shape. We're committed to making sure this works right, they are great skins!

Excellent report Tenno!  I was able to confirm your bug immediately using your detailed information.

Still don't see this.   Tried running DX10, low detailed, window,  frame-capped to 30. Skeptical that it's performance related at all since some of you have pretty strong PCs. Tried fishing from a zipline. Tried closing the fishing dialog by clicking button, vs pressing escape versus pressing spacebar.   Seems more likely to be a specific way that you're fishing which is why I asked for video of it starting from not-broken and then becoming broken :)  A screenshot where you've been fishing for half an hour and turned into a tentacle monster is not super useful to us.  Are you using vehicles? Using Controllers? Is it all fish types, all spears, or more specific?

I definitely want to help smash this but we have to narrow down what's causing it first

Today we will be starting a server script to fix player accounts that had a very specific pattern of purchases from Teshin's Steel Path Honors shop.

Script has finished running!  Nearly 12K player accounts were repaired.

In November of 2020 we introduced weekly items, that could be purchased once a week and would rotate over time.  Players who purchased two different items right at the start of this new offering could potentially end up with a broken account state where the purchase history was not properly unset, and the game would never allow you to purchase the item again. This has just come to light now because the special stock has gone through one complete rotation, and those players whose accounts were affected are unable to buy the item (an Umbra Forma Blueprint) that they should be able to.

The fix is a script that we will run on all player accounts which will allo...

This doesn't happen for me. Are you able to record a video showing the FIRST time you throw a spear and it creates an extra line?  Or describe in exact detail what you're doing

Thank you for the report, we are looking into these performance issues

15 hours ago, Alferciu said:

Hi, I had the same problem. Just noticed, googled it and found this thread.

I put 3 forma in my Voidrig, but actually 6 were consumed. 70pl wasted lol

Hope I can get support on that

I only went back a few days but I don't see anything weird: always spending forma 1 at a time. I'm definitely open to the possibility that bugs exist but I need more data like, a date this might have happened or a video demonstration of the issue to see what you are seeing.

I checked your account history and you're only ever spending 1 forma per mech polarize operation.  The real bug appears to be: the mech's "Amount of forma available" is counting aura and umbral formas, even though it shouldn't because those forma types are not applicable to the mech.  So for example, your UI says you have 3 forma,  but in reality you have 1 yellow forma (that can be used on mech)  plus an aura and umbra forma, so the next time you try to spend yellow forma the game will (correctly) say that you don't have any.

I'll put in a bug report for the misleading counter, let me know if that explains what you are seeing. 👍

On 2021-01-09 at 8:45 AM, (NSW)Gamer-Steve said:

Out of curiosity, would @[DE]Momaw be the right person to talk to about this

I can look, though usually a better idea to put such things in the Bug Reports subforum so entire team can observe rather than flagging an individual deep in an announcement thread :)

36 minutes ago, Duality52 said:

Both the Lobotricid and the Flagellocanth do not appear in the Codex, nor can they be placed in our Aquariums since Deimos Arcana. When will this be fixed?

Being able to put deimos fish in your aquarium was already addressed in a hotfix, have you tried recently? Still not seeing codex entries though, will get that looked at

Now that mechs have replaceable helmets, the skin and helmet are two different items.  In the next hotfix we will be retroactively giving everybody who bought the Day of the Dead and Snake skins their matching helmet parts.  You would just need to equip the DOTD helmet under the "head" slot once that patch arrives

2 hours ago, Syum_CZ said:

Fix Flagellocanth pls!!

ok!! :)

We're aware of this problem and we're investigating.  (This was collateral damage from allowing you to extract from missions as a mech)

The "semi automatic mode" is the alt fire, where it shoots a bouncing glaive-like projectile, and that should be inflicting status on every bounce. Is that not what's happening?  The shotgun primary firing mode has a very weak status chance, by design.

Thank you for the reports, I've confirmed that this is a problem and we'll look into it for our next update.